The 5 reasons XP can ’ t scale and what to do about them

XP seems to be a good method for small teams to develop high-power software system. There are concerns about the ability of the method to scale to scopes any larger than 12 developers. It only takes a small numb er of changes in the set of practices comprising XP to make it into a method scaleable to quite large scope. Indeed, modifying 5 practices and adding in a few new ones resolves the issues. 1 INTRODUCTION I have this belief about XP (and perhaps other " agile " development processes) about why they can't scale up, It's similar to why I had problems with heavyweight development process (think CMM) scaling down. In both cases, the approaches focus on a set of problems that exist in the target environment (small-scale development for XP) that don't exist in the other environment and miss important problems that don't exist in the intended environment but do exist in the other environment. In either case, you can't take the process and simply add more people (or in the case of CMM, take people away) and expect it to work.